Context and power control information management for proximity services

ABSTRACT

Management of context and power control information enables different power control schemes for point-to-point or point-to-multipoint based on proximity services or applications. Context information may be defined as situation data about a service or application that is used to help define a power control scheme to be implemented. Power control information may be defined as control or status data for power control, which can be used for reporting or controlling the transmitting power of a peer in a P2P network. Context and power control information may be managed across multiple layers such as the application layer, service layer, media access control layer, or physical layer. Context and power control information is updated and exchanged between or among peers for context-related power control in proximity services.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims benefit under 35 U.S.C. § 119(e) of ProvisionalU.S. Patent Application No. 61/834,335, filed Jun. 12, 2013, ofProvisional U.S. Patent Application No. 61/834,341, filed Jun. 12, 2013,and of Provisional U.S. Patent Application No. 61/837,993, filed Jun.21, 2013, the contents of all three of which are incorporated herein byreference in their entirety.

BACKGROUND

The Internet of Things (IoT) introduces objects or things toHuman-to-Human (H2H) based Internet services. It marks a stage of theInternet where physical or virtual objects are interconnected to enablethe Internet of Services (IoS). Many of these services are proximitybased, such as smart shopping, smart home, smart office, smart health,smart transportation, smart parking, smart grid, and smart city, amongother things.

Proximity services may be based on peer-to-peer (P2P) communications inproximity. P2P devices include tablets, smart phones, music players,game consoles, personal digital assistances, laptops/PCs, medicaldevices, connected cars, smart meters, sensors, gateways, monitors,alarms, set-top boxes, printers, Google glasses, drones, and servicerobots, among other things. A P2P communication system may be a centralsystem with a controller or core network serving as an infrastructure,or a distributed system without a controller or core network serving asthe infrastructure. Proximity services may include human-to-human (H2H)proximity services, machine-to-machine (M2M) proximity services,machine-to-human (M2H) proximity services, human-to-machine (H2M)proximity services, and network of network proximity services.

Proximity-based applications and services represent a trend to offloadheavy local internet traffic from a core infrastructure as well asprovide the connections to an infrastructure via multi-hopping. Manystandards have identified proximity services use cases as part of theirstandardization working groups, such as 3GPP, oneM2M, IETF, IEEE, andOMA. Service layer, as well as cross-layer techniques, is an area ofstandardization to enable these services.

Proximity services may use wireless networks that have varying transmitpower schemes. 3G or 4G wireless systems may use centralized control andimplement open loop transmit power control (TPC) or closed loop TPC.Centralized control entails control between a central controller (e.g.,base station, NodeB, or eNodeB) and a point (e.g., mobile station oruser equipment). Open loop TPC allows for the power level to be adjustedbased on the power target set by the central controller and the measuredchannel path loss. Closed loop TPC allows for the power level to beadjusted from the previous power level (open loop power setting) basedon the received signal quality and the power control bit(s) orcommand(s). WiMax IEEE 802.16 network TPC schemes are very similar tocellular systems with both open loop and closed loop power control.Bluetooth is an infrastructure-less short-range wireless system with amaster node and up to seven slave nodes with static transmitting power(typically around 20 dBm).

SUMMARY

Context information and power control information (CPCI) may be managedto enable proximity services with different context-related powercontrol procedures. The context-related power control procedures mayinclude CPCI detection, context-related inter-P2PNW power control, orcontext-related intra-P2PNW power control.

In an embodiment, a device may receive an indication of preparation fora transmission associated with a first proximity service of apeer-to-peer wireless network, wherein the first proximity service isoperating on the device. Responsive to receiving the indication, thedevice receives default context information for the first proximityservice operating on the device. The device scans wireless channels andalso receives context information from one or more peer devices. Thedevice determines its transmit power based on the default contextinformation and the first context information.

In another embodiment, a device receives a power control responsecomprising CPCI associated with a proximity service of a peer device.The context-related power control is executed to determine the transmitpower based on the CPCI associated with the proximity service of thepeer device and the device.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to limitations that solve anyor all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description,given by way of example in conjunction with the accompanying drawingswherein:

FIG. 1 illustrates examples of how CPCI may be communicated;

FIG. 2 illustrates an exemplary scenario for context-related powercontrol management;

FIG. 3 illustrates cross-layer context power control information (CPCI)in proximity;

FIG. 4 illustrates an exemplary method for general context-related powercontrol;

FIG. 5 illustrates a system of peers proximal to each other;

FIG. 6 illustrates an exemplary call flow that illustrates the use ofCPCI detection, in accordance with one embodiment;

FIG. 7 illustrates an exemplary call flow for inter-P2PNW management, inaccordance with one embodiment;

FIG. 8 illustrates an exemplary call flow for intra-P2PNW management, inaccordance with one embodiment;

FIG. 9 illustrates an exemplary method for CPCI management forintra-P2PNW multi-application power control, in accordance with oneembodiment;

FIG. 10 illustrates an exemplary method for point-to-multipointcontext-related power control, in accordance with one embodiment;

FIG. 11A illustrates an exemplary, non-limiting modified and/or extendedgeneral MAC frame format according to an embodiment;

FIG. 11B illustrates an exemplary, non-limiting frame control fieldformat according to an embodiment;

FIG. 12A is a system diagram of an example machine-to-machine (M2M) orInternet of Things (IoT) communication system in which one or moredisclosed embodiments may be implemented;

FIG. 12B is a system diagram of an example architecture that may be usedwithin the M2M/IoT communications system illustrated in FIG. 12A;

FIG. 12C is a system diagram of an example M2M/IoT terminal or gatewaydevice or a peer that may be used within the communications systemsillustrated in FIGS. 2, 3, 5, 12A, and 12B; and

FIG. 12D is a block diagram of an example computing system in whichaspects of the communication system of FIGS. 2, 3, 5, 12A, and 12B maybe embodied.

DETAILED DESCRIPTION

Conventional power control schemes implemented or proposed by otherwireless communication systems, such as 3GPP, WiMax 802.16, WiFi 802.11,WPAN 802.15, and Bluetooth, among others, do not support managingcontext information and power control information (hereinafter CPCI) forpower control schemes with regard to proximity services (ProSs), asdiscussed herein. Disclosed herein are approaches for context-relatedpower control management that may include, but are not limited to, themanagement of CPCI for an infrastructure-less system (e.g., inter-P2PNWsand intra-P2PNW), the management of CPCI for multi-service at a peer(e.g., multiple ProSs used at the same time), or the management of CPCIfor point-to-multipoint communications when using multicastcommunications.

Wireless peer-to-peer networks (P2PNWs) may be formed for proximityservices (ProSs). Proximity may be considered a relatively small area inwhich the peers can communicate with each other, usually via direct ormulti-hopped radio signals. Different ProS P2PNWs use different powercontrol schemes. For example, the power control scheme for a gaming ProSP2PNW with peers inside a few meters may not emphasize path losscompensation for the near-far problem or frequent power adjustments dueto mobility. Whereas a ProS P2PNW within a department store forpersonalized advertisement may require path loss compensation for thenear-far problem and frequent power adjustments due to mobility.

Many ProS P2PNWs coexist within a short radio range of each otherwithout a central controller to manage the ProS devices among the ProSP2PNWs (e.g., inter-P2PNWs) and within the ProS P2PNWs (e.g.,intra-P2PNWs). ProS P2PNWs that are in radio range are vulnerable tointerferences caused by other nearby ProS P2PNWs. CPCI may be used tohelp in the management of power control for inter-P2PNWs andintra-P2PNWs and therefore minimize the interference among differentProS P2PNWs as well as within a P2PNW.

A device may engage in multiple ProSs at the same time and differentProSs may have different requirements for power control. Therefore,context-related power control information management for multipleapplications or services on a device may be used to support multipleproximity services at the same time. ProSs as discussed herein may referto applications or services.

ProS P2PNWs are formed in proximity with the desired contexts, such asservices, users, devices, service range, location, etc., between twopeers (pair communication) or among peers (group communication). Forexample, at a shopping mall, there may be P2PNWs for social connection,P2PNWs for streaming or content exchange, P2PNWs for broadcasting ormulticasting stores' promotions or personalized advertisements, andP2PNWs for gaming, among other things. These ProS P2PNWs have differentrequirements for power control due to the required QoS of each service.Therefore, an effective power control scheme may be defined by cateringto the particular service or context. CPCI based on services or contextenables different power control schemes for different ProS P2PNWs.

ProS-based context information generally may be defined as situationdata about a service or application that is used to help define a powercontrol scheme to be implemented. For example, as briefly shown in Table1, context information may include information, such as a service powercategory (SPcat), service range (SerR), power control interval (PCInt),bandwidth (BW), data rate (DR), modulation and coding scheme (MCS),latency (Lat), location (Loc), speed (Sd), or the like. Each type ofProS-based context information listed in Table 1 is described in moredetail below.

TABLE 1 Proximity Service Based Context Information Description ServicePower Category Classification of power control requirements (SPcat)Service Range (SerR) Service radio range for a ProS P2PNW Bandwidth (BW)Bandwidth allocated for a peer Data Rate (DR) Data rate for a ProS Powercontrol interval Period for updating CPCI and adjusting (PCInt)transmitting power level Modulation and Coding Modulation and codingused for a proximity Scheme (MCS) service Latency (Lat) Delay tolerancefor a proximity service Location (Loc) Location of a peer for aproximity service Speed (Sd) Speed for a proximity service

ProS-based power control information may be defined as control or statusdata for power control, which can be used for reporting or controllingthe transmitting power of a peer's transceiver. For example, powercontrol information may include information, such as transmit power(TxP), maximum transmit power (MaxTxP), minimum transmit power (MinTxP),power adjustment (PAdj), endpoint (EP), path loss (PL), received signalquality (RxSQ), or the like, which are briefly shown in Table 2 anddiscussed in more detail below.

TABLE 2 Proximity Service Based Power Control Information DescriptionTransmit Power (TxP) TxP is the power level of a transmission during aPCInt from a transmitter in a ProS P2PNW. Maximum Transmit MaxTxP ismaximum power level allowed for Power (MaxTxP) transmission for a ProSP2PNW. Minimum Transmit Minimum power level required for Power (MinTxP)transmission for a ProS P2PNW Power Adjustment Power adjustment forinitial or open loop (PAdj) context-related power control Endpoint (EP)The endpoint or receiver of a transmission within a ProS P2PNW. PathLoss (PL) The attenuation or propagation loss through the wirelesschannel Received Signal Quality The received signal quality may beindicated (RxSQ) by the measured Received Signal Strength Indicator(RSSI), received Signal Interference Noise Ratio (SINR), or ChannelQuality Indicator (CQI), etc.

FIG. 1 provides several examples of how CPCI may be transmitted amongpeers. Here, it is assumed that the communication is processed fromright to left, as shown by arrow 251. As shown in FIG. 1, based on theimplementation and proximity service involved, there may be differentCPCI transmitted and relied upon for context-related power controlmanagement. For example, a first ProS may operate sufficiently withdefault values and only transmit updates to BW at a first time period,while transmitting updates to EP and PCInt at a second time period.Communication 241 is an example of CPCI 245 transmitted within a beacon.A peer in proximity may detect the CPCI 245 inserted in communication241. Communication 242 is an example of CPCI 246 broadcast on a commonchannel, such as a common control channel or common data channel.Communication 242 may also be broadcast on a broadcasting channel,paging channel, or the like. A peer in proximity may detect CPCI 246inserted in communication 242. Communication 243 is an example of CPCI247 transmitted in a transmission frame positioned after control data248. The type of CPCI 247 within communication 243 may be indicative ofa peer device engaged with multiple end-points or receivers in same ordifferent ProS P2PNWs. In a scenario of the same Pros P2PNW, this is anexample of exchanging CPCIs for group based communications, i.e. thetransmitter piggy backs the transmitting power to each end-point(receiver) in the control or data message. Communication 244 is anexample of CPCI transmitted in a transmission frame positioned beforecontrol data 250. CPCI 249 includes TxP, RxSQ, and PAdj, which may beindicative of control information for power control response, orinformation for closed loop power control with required power adjustmentfrom a receiver. The exact location of CPCI, and the manner in which itis transmitted among peers, may vary across different implementation ofCPCI for context-related power control, and the present disclosure is byno means limited to any one of the types of communications in which CPCIis shown as being transmitted in FIG. 1.

An example of a CPCI use case is illustrated in FIG. 2 with furthercorresponding details in Table 3. FIG. 2 illustrates an exemplaryscenario for context-related power control management. P2PNW 101 (i.e.,ellipse 101) contains a plurality of peers that are communicating usingcentralized group communication.

A peer may be a tablet, smart phone, music player, game console,personal digital assistant, laptop, PC, medical device, connected car,smart meter, home gateway, monitor, alarm, sensor, set-top box, printer,a mobile station (MS) in a 2G network, a user equipment (UE) in a 3Gnetwork, or one or a group of full-function devices (FFDs) orreduced-function devices (RFDs) in IEEE 802.15 (wireless personal areanetwork (WPAN)) networks. As one example, a peer may have the hardwarearchitecture illustrated in FIG. 12C (described more fully below) or avariation thereof, or it may have the architecture of the computingsystem illustrated in FIG. 12D (also described more fully below).

Referring still to FIG. 2, the peers in P2PNW 101, such as peer 110,peer 113, peer 116, and peer 117, are in communication with each othervia several dispersed CPCI management aggregation points hereinaftercalled virtual leaders. A virtual leader (e.g., peer 116) is a peer thatmay be dynamically selected to represent, manage, and coordinate the P2Pcommunications among a group of peers sharing the same ProS, i.e. withina P2PNW, for centralized intra-P2PNW control. A super virtual leader(not shown) is a virtual leader defined to coordinate all virtualleaders of P2PNWs in proximity for centralized inter-P2PNWs control. Avirtual leader and super virtual leader may be used for the purposes ofsynchronization, power control, interference management, channelallocation, access control, or the like.

Each P2PNW in FIG. 2 may have different ProSs implemented. For example,the peers within P2PNW 101 may communicate with each other by the use ofa video conference ProSs. As another example, the peers within P2PNW 102may communicate with each other by the use of a chat ProSs and may beinvolved in a pair communication. The peers within P2PNW 103 maycommunicate with each other by the use of a keep alive ProSs and may beinvolved in a pair communication. The peers within P2PNW 104 maycommunicate with each other by the use of a gaming ProS and may beinvolved in a distributed group communication. In a distributed groupcommunication, each peer of a P2PNW manages all control relatedcommunications with other peers of P2PNWs in proximity, which maycommunicate over a common channel, broadcasting channel, paging channel,or the like.

Thus, in the example of FIG. 2, the ProSs of P2PNW 101, P2PNW 102, P2PNW103, and P2PNW 104 have peers with different contexts. As illustrated inTable 3, the ProSs shown in FIG. 2 may have different recommendedcontext information and power control information settings. As describedin more detail below, understanding the context of different ProSs mayallow for the optimization of transmit power to support a preferredquality of service level of a ProS, while minimizing wireless radiointerference and power consumption, among other things.

TABLE 3 Application Context Info Power Control Info Video Conf. 1.Service Power Category: 1. Max. Tx Power: medium Meeting e.g. Spcat1 -very high data 2. Power Control Interval: rate & low error rate long 2.QoS: 1-to-N group based - 3. Measurements at Rx: guaranteed or besteffort to SINR, CQI, etc. all peers 4. Info from Tx: Tx power 3. ServiceRange: medium level, location, etc. Gaming 1. Service Power Category: 1.Max. Tx Power: medium e.g. SPcat2 - high data rate 2. Power ControlInterval: & low error rate long 2. QoS: distributive group 3.Measurements at Rx: based - guaranteed to all SINR, CQI, etc. peers 4.Info from Tx: Tx power 3. Service Range: small level, location, etc.Chat 1. Service Power Category: 1. Power Control Interval: e.g. SPcat3 -low data rate medium & high error rate 2. Measurements at Rx: 2. QoS:average SINR, RSSI, etc. 3. Info from Tx: Tx power level, speed, etc.Keep Alive 1. Service Power Category: 1. Measurements at Rx: e.g.SPcat4 - very low data RSSI, etc. rate & high error rate 2. Info fromTx: Tx power 2. QoS: low level, speed, etc.

As illustrated in FIG. 3, CPCI may be managed across multiple layersthat may include service layer 120, MAC layer 122, and physical layer121. There may be an application layer above service layer 120. In anembodiment, CPCI may be maintained at service layer 120 or anapplication layer (not shown) for default CPCI and at physical layer 121or MAC layer 122. ProS may be located at service layer 120 orapplication layer (not shown) above service layer 120. In FIG. 3, ProS123 may update CPCI during a session of transmitting and receiving,based on detected information or measured results at a power controlfunction 125 located at physical layer 121. The power control functionof a device is a hardware and/or software module executing on aprocessor of the device that controls the transmission power of thedevice's transmitter. The updated CPCI values at power control function125 may be fed back to higher layers, such as ProS 123 of service layer120. Also shown in FIG. 3, CPCI may also be exchanged at low layersbetween or among peers for context-related power control to ensurereliable proximity services. Power control function 125 associated withProS 123 may communicate with power control function 126 of physicallayer 128. The power control function may be implemented at physicallayer 121 or MAC layer 122 in order to minimize latency and meet anylatency requirements. Some or all of the power control function may beat the service layer 120 or application layer, e.g. defining the defaultparameter values based on the ProS and overriding lower layer (e.g., MACor PHY) power control values, among other things.

Disclosed hereinafter are schemes for managing CPCIs across layers andexchanging CPCIs between or among peers in proximity. Context-relatedpower control may enable more reliable and efficient IoT proximityservices. Context-related power control mechanisms, generally described,may include general context-related power control, context-relatedmulti-application power control, and context-related Intra-P2PNWpoint-to-multipoint power control. General context-related powercontrol, context-related multi-application power control, andcontext-related Intra-P2PNW point-to-multipoint power control mayinvolve CPCI detection, inter-P2PNWs power control, intra-P2PNWs powercontrol, and CPCI management.

FIG. 4 illustrates an exemplary method for general context-related powercontrol, in accordance with one embodiment. At step 131, default CPCIpasses to the power control function of a peer. The power controlfunction may receive from a service layer (or other layer, such as theapplication layer) on the first peer a default CPCI that waspreconfigured (e.g., manually configured by the user or automaticallyconfigured by the application or service layer at initial activation ofthe first peer or ProS) or updated from a previous session (e.g.,automatically updated during a previously connected ProS session). Atstep 132, the first peer receives CPCI from peers in proximity byscanning channels, such as beacon, paging, or broadcast channels. Insituations where there is no CPCI detected in proximity, a defaultminimum TxP or TxP based on historical records (e.g., previous averagesor mean TxPs) or default values based on the power control category(PCat) may be used. At step 133, the first peer determines a first TxP.Here, the first peer may determine the first TxP level based on defaultCPCI values (e.g., step 131), which may be passed from a higher layer,as well as CPCI values received from peers in proximity (e.g., step132).

With continued reference to FIG. 4, at step 134, the first peerbroadcasts power control request or piggy backed with control or datatransmission at a common channel at the first TxP. At step 135, thefirst peer receives from a second peer in proximity a response that mayinclude the CPCI of the second peer (e.g., CPCI may have the poweradjustment (PAdj) and other CPCI for first peer). The second peer maysend more than one CPCI, which may be related to each proximity serviceon the second peer or group of peers being managed by the second peer ifthe second peer is a virtual lead. At this step, the second peer (thisis also applicable to a plurality of peers) need only be in proximityand not necessarily using the same ProS as the first peer forinter-P2PNWs power control. At step 136, based on the updated CPCI, thefirst peer recalculates TxP using the power control function and adjustsits TxP accordingly, which results in a second TxP of the first peer. Atstep 137, after the use of the inter-P2PNW associated TxP (i.e., secondTxP) of step 136, the first peer may receive CPCI associated with afirst ProS in use on the first peer for intra-P2PNW power control. Atstep 138, based on the received first ProS related CPCI of step 137, thesecond TxP may be adjusted to a third TxP. When multiple peers areinvolved, the first peer may consider received CPCI from each peer andadjust the TxP that is appropriate for the ProS(s). For example, ifthere are a plurality of peers, the first peer may average or use themaximum or minimum of the optimal TxPs it calculates for each peer.

Still referring to FIG. 4, step 132 may be considered a CPCI detectionstep. Step 133 through step 136 may be considered inter-P2PNW powercontrol steps. And step 137 and step 138 may be considered intra-P2PNWpower control steps. CPCI detection, inter-P2PNW power control, andintra-P2PNW power control information call flows are discussed in moredetail below.

FIG. 5 illustrates a system 140 including peers proximal to each other,similar to FIG. 2, where CPCI may be used for context-related powercontrol. FIG. 5 uses ovals to illustrate the P2PNW for each ProSutilized by a peer. The ovals should not be interpreted as a radio rangeor the like of a peer. Peer 146 utilizes a P2PNW for ProS 141 and aP2PNW for ProS 142, peer 147 utilizes a P2PNW for ProS 141 and a P2PNWfor ProS 143, and peer 145 utilizes a P2PNW for ProS 144. Asillustrated, peer 146 and peer 147 both utilize the P2PNW for ProS 141.Peer 145 may communicate with one or more other peers (not shown) withinthe P2PNW for ProS 144. Peer 146 and peer 147 may also communicate withone or more other peers (not shown) within the P2PNW for ProS 142 andP2PNW for ProS 143, respectively.

FIG. 6 illustrates an exemplary call flow 150 that considers the use ofCPCI detection in the system 140 of FIG. 5. As shown in FIG. 6, peer 146includes ProS 141 and power control function 152. At step 157, ProS 141on peer 146 (block 151) sends CPCI to power control function 152associated with ProS 141 on peer 146. CPCI of step 157 may be defaultCPCI values preconfigured or updated from previous sessions. It ispossible for other layers to store and send the default CPCI values. Atstep 158, peer 146 detects CPCI from various sources, such as block 153(ProS 142 on peer 146), block 154 (ProS 141 on peer 147), block 155(ProS 143 on peer 147), and block 156 (ProS 144 on peer 145). Peer 146may detect CPCI by scanning beacon, paging, broadcast channels, or thelike. The received CPCI of step 158 may include information associatingthe CPCI to a particular ProS and peer.

At step 159, peer 146 may determine its initial TxP based on defaultCPCI values (step 157), detected CPCI values (step 158), as well asmeasured CPCI values (e.g., measured RxSQ—not shown). TxP may be basedon an averaging of received TxP of the received CPCI or using the MinTxPdefault CPCI value, if no CPCI is received from another peer or ProS.The use of step 157 and step 158 may be based on ProS 141 of peer 146becoming re-enabled after an idle period (e.g., not using ProS 141) fora predetermined extended period of time. In addition, a process for CPCImanagement for inter-P2PNW power control (shown at 160) and a processfor CPCI management for intra-P2PNW power control (shown at 161) may beperformed after the completion of step 157 through step 159. It shouldbe noted that the peers in FIG. 6 and the other figures may be VLs orsuper VLs.

FIG. 7 is an exemplary call flow providing further details of theprocess 160 for CPCI management for inter-P2PNW power control in thecontext of system 140, in accordance with one embodiment. Duringinter-P2PNW CPCI management, a peer may collaborate with peers inproximity by exchanging CPCI on a common channel. At step 171, peer 146broadcasts (on a common channel) a power control request message (PCReq)associated with ProS 141. The PCReq may include the CPCI related to Pros141 of peer 146. The PCReq may be sent to peers in proximity, but notnecessarily participating in the same P2PNW for ProS 141.

At step 172, peer 146 receives responses (e.g., power control responses)that includes CPCI from various peers in proximity, such as block 153(ProS 142 on peer 146), block 154 (ProS 141 on peer 147), block 155(ProS 143 on peer 147), and block 156 (ProS 144 on peer 145). At step173, peer 146 adjusts the TxP based on the received responses of step172. The CPCIs may be exchanged and updated at a lower layer (e.g., PHYor MAC) and then sent to a higher layer (e.g., service or applicationlayer above TCP/IP in OSI model for infrastructure based communicationsystems or above MAC layer without TCP/IP layers for infrastructure-lesswireless system).

FIG. 8 is an exemplary call flow providing further details of theprocess 161 for CPCI management for intra-P2PNW power control in thecontext of system 140, in accordance with one embodiment. Here, CPCIassociated with ProS 141 is exchanged between peer 146 and 147, whichoperate within the same P2PNW for ProS 141. At step 185, peer 146 sendsto peer 147, at a predetermined first TxP, a power control request(PCReq) with CPCI related to ProS 141 on peer 146. The first TxP may bebased on a default CPCI value, a “CPCI detection” derived CPCI, anintra-P2PNW management derived TxP, or the like. At step 187, peer 147adjusts to a second TxP and updates its CPCI based on the CPCI receivedat step 185. At step 188, the updated CPCI of step 187 may be sent to ahigher layer (e.g., application layer associated with ProS 141) of peer147. At step 189, peer 147 sends a power control response (PCRes), atthe second TxP. The PCRes of step 189 may include the updated CPCI ofstep 187.

At step 190, peer 146, adjusts to a third TxP and updates its CPCI basedon the CPCI received at step 189. At step 191, peer 146 sends a controlor data message at the third TxP. The message of 191, may include theupdated CPCI of step 190. At step 192, the updated CPCI of step 190 maybe sent to a higher layer (e.g., application layer associated with ProS141) of peer 146. At step 193, peer 147 updates its CPCI based on thereceived CPCI of step 191 and at step 194 the updated CPCI is sent to ahigher layer. At step 195, peer 147 sends to peer 146 an acknowledgementthat peer 147 received the message of step 191. Periodically, CPCI maybe transmitted and TxP adjusted based on a predetermined time, such asPCInt. In an embodiment, if peer 146 sends a PCReq and a timely response(e.g., PCRes) is not received, then the TxP power may be incrementallyadjusted and a PCReq may be resent until a PCRes is received, apredetermined number of timeouts is reached, or the like.

As discussed herein, a peer can join one or more P2PNWs simultaneouslyin proximity. For example, with reference to FIG. 5, peer 146 mayinteract with peer 147 via chat using ProS 141 and may check anadvertisement or coupon broadcast from a store by another peer (notshown) associated with ProS 142. In this example, CPCI may need to bemanaged across applications on a device. When providing context-relatedpower control across multiple applications on single peer, CPCIdetection and inter-P2PNW power control management is similar to what isdiscussed in FIG. 6 and FIG. 7, respectively. Intra-P2PNW power controlwould be similar to what is discussed with regard to FIG. 8, but with anadded layer of complexity. For example, peer 146 adjusts TxP of eachtransmission to fit the determined TxP for the particular ProS used inthe transmission (e.g., a different TxP for chat ProS and anadvertisement ProS). More details are discussed below.

FIG. 9 illustrates an exemplary method for CPCI management forintra-P2PNW multi-application power control from the perspective of peer146 of system 146. At step 201 and step 202, peer 146 startscontext-related power control for ProS 141 and ProS 142, respectively.Step 202 and Step 203 may be triggered by an indication thattransmission needs to occur for a ProS. The indication may be a usercommand or automated occurrence based on a condition, such as time orreceiving data from a peer or other device. The indication may follow aninitial startup of the PRoS after a timeout based on idle time, devicereboot, or the like. At step 203 and step 204, CPCI detection may beutilized for ProS 141 and ProS 142 respectively. At step 205 and step206, inter-P2PNW management may be utilized for ProS 141 and ProS 142,respectively. At step 207, peer 246 determines whether ProS 141 needs totransmit. If yes, at step 209, in this implementation, context-relatedpower control procedures in the MAC/PHY layer for ProS 141 are appliedand a transmission occurs. After the transmission, at step 211, peer 146determines whether ProS 142 needs to transmit. If yes, at step 219, inthis implementation, context-related power control procedures in theMAC/PHY layer for ProS 142 are applied and a transmission occurs. If no,peer 146 continues to send transmissions based on context-related powercontrol procedures in the MAC/PHY layer for ProS 141. As shown in FIG.9, similar transmission analysis, with regard to context-related powercontrol procedures in the MAC/PHY layer for ProS 141 and ProS 142, wouldcontinue on peer 146 until context-related power control is aborted.

Many ProSs are group communication based via broadcasting ormulticasting, such as a ProS conference meeting with a presentingspeaker or a gateway that manages parking meters for smart parking.Point-to-multipoint intra-P2PNW CPCI management is similar to CPCImanagement for intra-P2PNW multi-application power control, as discussedabove, except that a central peer may multicast CPCI to multiple peersrather than unicast CPCI to each peer. A more detailed example is below.

FIG. 10 illustrates an exemplary method 230 for one-to-manycommunication for context-related power control with reference to system140 of FIG. 5. At step 231, peer 146 broadcasts or multicasts a powercontrol request to the peers in proximity that have ProS 141. The powercontrol request includes transmitting power level (e.g., in dBm) andlocation (e.g., absolute or relative geo-location). At step 232, peer147 (the closest receiver) replies with its power control response thatincludes transmitting power level (i.e. in dBm) and location ((i.e.absolute or relative geo-location). In this example, there are alsopeers (not shown) that are a farther distance away from peer 146 thanpeer 147. All peers respond to peer 146. At step 233, peer 146 evaluatesthe received CPCI and determines the power adjustment for peer 147 andeach other peer based on the calculated path loss from the receivedCPCI. At step 234, peer 146 determines the transmitting level based onthe power control category or the QoS of the service or application. Inthis example, there may turn out to be three quality of service levelsused. There may be a guaranteed quality of service defined astransmitting power=previous power+¼ dB for communications with a peerthat is the farthest distance away from peer 146. There may be besteffort quality of service defined as transmitting power=previous power−¼dB for communications with peer 147 (the near receiver). Lastly, theremay be an averaged quality of service defined as transmittingpower=previous power+averaged power adjustment for communications amongall other peers.

Table 1 and Table 2 above briefly discussed context information andpower control information. More details with regard to contextinformation and power control information are provided below. Asdisclosed above, context information may include information, such as aservice power category (SPcat), service range (SerR), power controlinterval (PCInt), bandwidth (BW), data rate (DR), modulation and codingscheme (MCS), latency (Lat), location (Loc), speed (Sd), or the like.

SPcat is a predetermined value that is indicative of a category forpower control requirements for different types of ProSs, such as publicsafety, healthcare, social networking, commercial advertisement, sensornetwork, or smart office, among others. The categories may be definedusing numeric, alphabetic, or alphanumeric values. For example, a firstcategory (e.g., SPcat=1) may be created for ProSs that may require ahigh data rate and high quality of service, among other restrictions orpreferences, and a second category (e.g., SPcat=2) may require a lowdata rate and a low quality of service. For example, healthcare ProSsmay be defined as SPcat=1, while a sensor network and chat applicationmay each be defined as SPcat=2. SPcat may be used to set a default powercontrol scheme. For example, when a ProS is first initialized thedefault TxP and other power control parameters may be set. This defaultscheme may be adjusted as context information and power controlinformation is received and analyzed on a peer.

SerR is context information that may be defined as the typical serviceradio range (i.e., distance) that is recommended for a predeterminedadequate quality of service for a ProS P2PNW. The service range can varybased on different ProSs. For example, the SerR between peers for apublic safety ProS may be 2 kilometers, while the SerR between peers ofa smart home proximity service may be 120 meters.

PCInt is context information that may be defined as the period forupdating or exchanging CPCI, as well as for adjusting the transmit powerlevel. For example, PCInt may be a relatively large value for a ProSP2PNW with very low or no mobility in order to save the overhead of CPCIexchanges between the transmitter and receiver, while PCInt may be arelatively small value for a ProS P2PNW with high mobility. Speed may bea factor in determining PCInt. PCInt may be considered power controlinformation or context information since is the period used for updatingCPCI or adjusting transmit power level.

BW, DR, and MCS are usually associated with each other. BW is contextinformation that may be defined as the bandwidth (e.g., Mbit/s) orsubcarriers (e.g., resource blocks) allocated for a peer in a ProSP2PNW. BW may be the typical BW to ensure a predetermined adequatequality of service or the BW available to a peer. Generally, a bandwidthis allocated commensurate with data rate ProSs and signal strength toensure a required or recommended throughput. DR may be defined as thetypical data rate to ensure a predetermined adequate quality of servicefor a ProS and may be defined as a measured data rate of a peer. MCS maybe defined as the modulation and coding scheme used for a ProS, such asdifferent methods for quadrature amplitude modulation (QAM), phase-shiftkeying (PSK), amplitude-shift keying (ASK), or the like. Highermodulation and coding schemes may involve high data rate ProSs, whichmay require higher maximum transmitting power to ensure the requiredthroughput.

Lat may be defined as the delay tolerance for a ProS. For example,emergency related ProSs may require very low Lat (e.g., milliseconds),while keep alive related proximity services may be able to tolerate highLat (e.g., seconds or minutes). Latency requirement may affect powercontrol interval (PCInt). For low latency services or applications, thePCInt value may be relatively small compared with high latency servicesor applications.

Loc may be defined as the location of a peer for a proximity service,such as geolocation, displacement from another site (e.g., 50 feetnorthwest from a P2PNW), or the like. Loc may be an absolute location(e.g., latitude and longitude) or relative to a peer. Loc may be used toestimate the path loss. For a fully distributed and infrastructurelesswireless system, there is no central controller, such as the NB or eNBin 3GPP cellular system, for managing the transmitting power control.Therefore, a peer may estimate the transmitting power level based on thepath loss derived from the other transmitter's location and transmittingpower level, as well as the received signal strength.

Sd may be defined as the typical speed of a peer to ensure apredetermined adequate quality of service for a ProS P2PNW. Sd also maybe defined as a measured speed of a peer. For example, a car on ahighway may travel at a high speed and may cause more channel variance,which may require relatively frequent power adjustment, i.e. lower valueof PCInt, when compared to a pedestrian speed. For some ProS, higherspeed may also cause performance degradation, which may requires highertransmitting power to ensure the throughput performance. A measuredspeed may be used to define PCInt.

Power control information, as discussed herein, may include information,such as transmit power (TxP), maximum transmit power (MaxTxP), minimumtransmit power (MinTxP), power adjustment (PAdj), endpoint (EP), pathloss (PL), received signal quality (RxSQ), or the like.

TxP may be the typical power level (e.g., dbm) that may ensure apredetermined adequate quality of service for a ProS P2PNW or also maybe defined as a measured TxP at a particular time. This value may beadjusted during the closed loop power control. MaxTxP is a maximum powerlevel allowed for transmission for a ProS P2PNW that may ensure apredetermined adequate quality of service for a ProS P2PNW or the MaxTxPavailable to a transmitter. If a transmitter reaches its MaxTxP value,it cannot increase the transmitting power level any more, even if thecalculated power adjustment is “increasing power” during either open orclosed loop power control. MinTxP is a minimum power level required fortransmission for a ProS P2PNW that may ensure a predetermined adequatequality of service for a ProS P2PNW or the MinTxP available to atransmitter. Usually a transmitter starts transmitting with its MinTxP,if there is not enough other information for estimating the initialpower level.

PAdj is power adjustment for initial, closed, or open loopcontext-related power control. PAdj may be a relative value from thecurrent power level (e.g., decrease by 0.5 db) or instruction totransmit within a range (e.g., less than 10 dbm).

EP is the end-point (i.e., receivers) in a group based communicationeither one-to-many broad/multi-cast or one-to-one unicast within thegroup. The EP value may be the EP's identifier (e.g., peer or deviceidentifier) which is locally unique within the P2PNW. EP could be mappedfrom MSISDN to a locally unique shorter ID, or other peer or deviceidentifier

Other power control information may be PL and RxSQ. PL is theattenuation or propagation loss through the wireless channel. PL is usedfor estimating the initial power level or calculating the next poweradjustment. PL may be a relative value, such as 10 db. RxSQ may be usedfor estimating the initial power level or calculating the next poweradjustment. RxSQ may be indicated by the measured received signalstrength indicator (RSSI), received signal interference noise ratio(SINR), or channel quality indicator (CQI), or the like.

CPCI, as discussed herein, may be a category designation that signifiesa range rather than an absolute value. For example, Sd may be acategory, such as “pedestrian speed,” which may indicative of a speedbetween 1 and 5 kilometers per hour. Alternatively, Sd, for example, maybe an absolute value such as 4.75 kilometers per hour. The category andabsolute value concepts may apply to Loc, MCS, Lat, DR, BW, PCInt, andSerR, among other context information or power control information. CPCImay be updated based on historical data.

As discussed above in connection with FIG. 1, CPCI may be transmittedamong peers in a variety of ways. In addition to the options illustratedin FIG. 1, in other embodiments, modified or extended IEEE 802.15 or802.11 MAC frames may be employed to facilitate transmission of CPCI, aswell as new Information Elements (IE)s. In one embodiment, a new frameformat may be used that may be a general MAC frame with new fields inthe MAC header that are related to context information that facilitatesthe power control procedures described herein. New management frames mayalso be used to support power control requests and responses. Furtherdetail about these frames and IEs is provided below.

FIG. 11A illustrates one embodiment of a modified MAC frame format 400that may be used in connection with the power control proceduresdescribed herein. In FIGS. 11A and 11B, fields indicated in bold,italic, and underline are new or modified fields and may include newsub-fields. Other fields may have the same meaning as defined in theexisting IEEE 802.15.4 and 802.11 standards.

As shown, the frame 400 generally comprises a MAC header 402 and MACpayload 404. In one embodiment, all fields in the frame may be requiredexcept the auxiliary fields 416 and auxiliary security header 418. In anembodiment, the sequence number field 408 and auxiliary security header418 may have the same meaning as defined in the IEEE 802.15.4 standard.

In this embodiment, the frame control field 406 carries controlinformation, such as the frame type, required type of acknowledgementmessage, and addressing mode. FIG. 11B illustrates one embodiment of aformat 500 of the frame control field. In an embodiment, the frame type,frame pending, frame version, security enabled, and IE present fieldsmay have the same meaning as defined in the IEEE 802.15.4 standard. Inone embodiment, all the fields in this frame control fields 406 may bemandatory.

Frame type and subtype fields 424, 426 may be mandatory and together mayindicate the type of a frame, i.e., the function of a frame. In oneembodiment, there are four basic frame types: beacon, management, data,and acknowledgement. Each type of frame may have several subtypes. Inaddition, the meaning of subtype fields may vary for different frametypes. In one embodiment, management frames may have a Frame Type Valueof “1,” and a Frame Subtype value of “8” may be used to identify theframe as a “power control request” frame, and a Frame Subtype value of“9” may be used to identify the frame as a “power control response”frame. Other Frame Subtype values may be used to identify other types ofmanagement frames.

Referring still to FIG. 11B, in an embodiment, a required ACK type field428 in the frame control field 406 may specify what type of acknowledgeframe is expected. For example, the required ACK type field may be setas shown in Table 4 below.

TABLE 4 Values of the Required ACK Type Field 428 Required ACK TypeValue Type of ACK Required 0 No ACK 1 Individual ACK 2 Aggregated ACK 3Conditional ACK 4 Group ACK 5 Cross-layer ACK 6 Cross-application ACK 7Cross-layer and Cross- application ACK 8 Fragment incremental ACK (IACK)

Referring back to FIG. 11A, addressing fields may consist of one or moreof a source address, a destination address, a transmitting hop address,and a receiving hop address. Source address and destination addressfields may carry the source and destination address of a frame.Transmitting hop address and receiving hop address fields may bereserved for multi-hop scenarios, carrying the address information ofthe intermediate peers. A transmitting hop address is an address of thepeer sending this frame. The receiving hop address is the address of thepeer to receive this frame. The presence of a transmitting hop addressand/or a receiving hop address field may be indicated by the addressingfields indication.

As shown in FIG. 11A, the MAC frame format 400 may further include anaddressing fields indication field 410 that may contain an indication ofthe presence of a transmitting hop address and a receiving hop addressin the addressing fields 412. While a source and destination address mayalways be present in addressing fields 412, the presence of atransmitting hop address and a receiving hop address may be optional fora multi-hop scenario. For example, for one-hop transmission, neither ispresent, for the first hop in a multi-hop transmission (i.e., theoriginal source is sending the frame) only a receiving hop address ispresent and the transmitting hop address is the same as the sourceaddress, for the last hop in a multi-hop transmission only atransmitting hop address is present and the receiving hop address is thesame as the destination address, and for other hops in a multi-hoptransmission, both a transmitting hop address and a receiving hopaddress are included. In addition, a frame may be a relayed frame whenthe addressing fields indication is set up as in the last two examples(last hop and other hops).

As further shown in FIG. 11A, a P2PNW/APP ID field 414 field may containa P2P network ID or application ID. All peers joining a P2P network (NW)may have a locally unique P2PNW/APP ID. If a P2PNW ID is not determinedwhen a frame is sent, this field may carry an application ID. Because aP2PNW may be formed by an application or service, a P2PNW ID may be anetwork identifier that may be used to define and differentiate anapplication-specific P2PNW. Due to the distributed nature of proximityservices, a P2PNW ID may be locally unique.

A P2PNW ID may include but is not limited to, a CAID or application IDthat indicates the desired service or application (e.g., Facebook forsocial networking, Netflix for video streaming, etc.), locationinformation indicating the location of the P2PNW, an ID of the peer thatgenerated the P2PNW ID, and a network sequence number that may be usedto differentiate existing P2PNWs with the same context information. AP2PNW ID may be generated using different structures, such as aconcatenated structure where each piece of information is assigned withsome information bits and all information pieces are concatenated or aparallel structure where all pieces of information are added togetherthrough some mathematical calculation, such as XOR and hash.

Based on different control schemes, a P2PNW ID may be generated andassigned by different parties in the network. In a centralized controlscheme embodiment, a P2PNW ID may be generated by a SuperVL that thennotifies the VL(s), or a VL may generate the P2PNW ID and broadcast itin a beacon to notify the SuperVL and other VLs. In a hybrid controlscheme embodiment, a VL may generate a P2PNW ID and broadcasts it in abeacon to notify other VLs. In a distributed control scheme embodiment,a peer that wants to form a P2PNW (i.e., a peer that defines a newapplication frame) may generates a P2PNW ID and broadcast a beacon tonotify every peer within the proximity of the P2PNW ID.

Still referring to FIG. 11A, an Auxiliary Fields field 416 may containfields that are optional but important for some functionalities. Forexample, a context category field may be included that indicates anapplication or service category, such as emergency service, socialnetworking, smart office, etc. As another example, a hopper indicationfield may be included that indicates whether a frame sender is willingto relay other frames for a multi-hop discovery process.

As mentioned above, power control request frames (e.g., Frame Type=1;Frame Subtype=8) may be used to request context and power controlinformation within proximity. Table 5 lists some exemplary additionalfields that may be provided in the MAC payload (e.g., the Frame Payloadfield 422 of the MAC Payload 404 of frame format 400) of a power controlrequest frame, in accordance with one embodiment. In one embodiment, theinformation in Table 5 may be exchanged only once within proximity. Onlywhen any of this information is changed will it be included in a powercontrol request for information exchange. Other power control relatedinformation, such as service power category, transmission power, andreceived signal quality, may be included in one or more CPCI IEs, asfurther described below.

TABLE 5 Fields in an example Power Control Request Frame Mandatory/Field Description Option Power Indicate how frequent the sender willstart a M control power control procedure in for the applicationinterval with the service power category shown in CPCI IE Maximum Upperlimit of power level that could be used M tx power by the sender.Minimum Lower limit of power level that could be used M tx power by thesender. Service Indicate the typical service radio range for a O rangeProS P2PNW. The service range can vary greatly with different proximityservices. For example, the service range for public safety proximityservice will be significant larger than the service range of a smarthome proximity service. Bandwidth Indicate the bandwidth or subcarriersallocated O for the sender in a ProS P2PNW

In an embodiment, a power control response may be sent when a peerreceives a power control request message. As described above, a powercontrol response message may provide the power control information ofthe peer receiving the power control request to the requestor. Theinformation included in a power control response message is similar tothe information provided in a power control request.

An Information Element (IE) may provide a flexible, extensible, andeasily implementable way to encapsulate information for efficientmessage exchange. An IE may be either part of a MAC header or a MACpayload. In the example frame format 400 illustrated in FIG. 11A, afield 420 is provided for holding IEs. Multiple IEs may be concatenatedin one frame.

Table 6 below lists example fields of an IE for carrying CPCI in a powercontrol request or response frame.

TABLE 6 Fields in CPCI IE Mandatory/ Field Description Option IEidentifier Identify the type of IE M IE length Indicate the total lengthof the IE M Tx power Indicates the transmission power that is used M tosend the message Service Indicate the sender's power control M powerclassification according to the power control category requirements fordifferent types of proximity services or applications, such as publicsafety, social networking, commercial advertisement, sensor network,smart office, etc. Rx signal indicates the received signal quality,e.g., O quality or RSSI or the estimated path loss based on path lossthe previous transmission between transmitter and receiver Power Carrythe recommendation for the expected O adjustment receiver on how toadjust the transmission power to make the transmission more reliable

In other embodiments, CPCI information may be carried in an 802.15 or802.11 beacon frame, having new or modified fields similar to thoseillustrated in FIG. 11A.

FIG. 12A is a diagram of an example machine-to machine (M2M), Internetof Things (IoT), or Web of Things (WoT) communication system 10 in whichone or more disclosed embodiments may be implemented. Generally, M2Mtechnologies provide building blocks for the IoT/WoT, and any M2Mdevice, gateway or service platform may be a component of the IoT/WoT aswell as an IoT/WoT service layer, etc.

As shown in FIG. 12A, the M2M/IoT/WoT communication system 10 includes acommunication network 12. The communication network 12 may be a fixednetwork (e.g., Ethernet, Fiber, ISDN, PLC, or the like) or a wirelessnetwork (e.g., WLAN, cellular, or the like) or a network ofheterogeneous networks. For example, the communication network 12 maycomprise of multiple access networks that provides content such asvoice, data, video, messaging, broadcast, or the like to multiple users.For example, the communication network 12 may employ one or more channelaccess methods, such as code division multiple access (CDMA), timedivision multiple access (TDMA), frequency division multiple access(FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and thelike. Further, the communication network 12 may comprise other networkssuch as a core network, the Internet, a sensor network, an industrialcontrol network, a personal area network, a fused personal network, asatellite network, a home network, or an enterprise network for example.

As shown in FIG. 12A, the M2M/IoT/WoT communication system 10 mayinclude the Infrastructure Domain and the Field Domain. TheInfrastructure Domain refers to the network side of the end-to-end M2Mdeployment, and the Field Domain refers to the area networks, usuallybehind an M2M gateway. The Field Domain includes M2M gateways 14 andterminal devices 18, which may be peers as disclosed above. It will beappreciated that any number of M2M gateway devices 14 and M2M terminaldevices 18 may be included in the M2M/IoT/WoT communication system 10 asdesired. Each of the M2M gateway devices 14 and M2M terminal devices 18are configured to transmit and receive signals via the communicationnetwork 12 or direct radio link in proximity. The M2M gateway device 14allows wireless M2M devices (e.g. cellular and non-cellular) as well asfixed network M2M devices (e.g., PLC) to communicate either throughoperator networks, such as the communication network 12 or direct radiolink. For example, the M2M devices 18 may collect data and send thedata, via the communication network 12 or direct radio link inproximity, to an M2M application 20 or M2M devices 18. The M2M devices18 may also receive data from the M2M application 20 or an M2M device18. Further, data and signals may be sent to and received from the M2Mapplication 20 via an M2M service layer 22, as described below. M2Mdevices 18 and gateways 14 may communicate via various networksincluding, cellular, WLAN, WPAN (e.g., Zigbee, 6LoWPAN, Bluetooth),direct radio link in proximity, and wireline for example.

Referring to FIG. 12B, the illustrated M2M service layer 22 in the fielddomain provides services for the M2M application 20, M2M gateway devices14, and M2M terminal devices 18 and the communication network 12. AProS, as described herein, may be a M2M Application 20 or M2M ServiceLayer 22. It will be understood that the M2M service layer 22 maycommunicate with any number of M2M applications, M2M gateway devices 14,M2M terminal devices 18, and communication networks 12 as desired. TheM2M service layer 22 may be implemented by one or more servers,computers, or the like. The M2M service layer 22 provides servicecapabilities that apply to M2M terminal devices 18, M2M gateway devices14 and M2M applications 20. The functions of the M2M service layer 22may be implemented in a variety of ways, for example as a web server, inthe cellular core network, in the cloud, etc.

Similar to the illustrated M2M service layer 22, there is the M2Mservice layer 22′ in the Infrastructure Domain. M2M service layer 22′provides services for the M2M application 20′ and the underlyingcommunication network 12′ in the infrastructure domain. M2M servicelayer 22′ also provides services for the M2M gateway devices 14 and M2Mterminal devices 18 in the field domain. It will be understood that theM2M service layer 22′ may communicate with any number of M2Mapplications, M2M gateway devices and M2M terminal devices. The M2Mservice layer 22′ may interact with a service layer by a differentservice provider. The M2M service layer 22′ may be implemented by one ormore servers, computers, virtual machines (e.g., cloud/compute/storagefarms, etc.) or the like.

Referring also to FIG. 12B, the M2M service layer 22 and 22′ provide acore set of service delivery capabilities that diverse applications andverticals can leverage. These service capabilities enable M2Mapplications 20 and 20′ to interact with devices and perform functionssuch as data collection, data analysis, device management, security,billing, service/device discovery etc. Essentially, these servicecapabilities free the applications of the burden of implementing thesefunctionalities, thus simplifying application development and reducingcost and time to market. The service layer 22 and 22′ also enables M2Mapplications 20 and 20′ to communicate through various networks 12 and12′ in connection with the services that the service layer 22 and 22′provide.

In some embodiments, M2M applications 20 and 20′ may include desiredapplications that communicate CPCI using context-related power controlmessages that may include PCReq and PCRes, as discussed herein. The M2Mapplications 20 and 20′ may include applications in various industriessuch as, without limitation, transportation, health and wellness,connected home, energy management, asset tracking, and security andsurveillance. As mentioned above, the M2M service layer, running acrossthe devices, gateways, and other servers of the system, supportsfunctions such as, for example, data collection, device management,security, billing, location tracking/geofencing, device/servicediscovery, and legacy systems integration, and provides these functionsas services to the M2M applications 20 and 20′.

Proximity services of the present application may be implemented as partof a service layer. The service layer is a software middleware layerthat supports value-added service capabilities through a set ofApplication Programming Interfaces (APIs) and underlying networkinginterfaces. An M2M entity (e.g., an M2M functional entity such as adevice, gateway, or service/platform that may be implemented by acombination of hardware and software) may provide an application orservice. Both ETSI M2M and oneM2M use a service layer that may containthe proximity services of the present invention. ETSI M2M's servicelayer is referred to as the Service Capability Layer (SCL). The SCL maybe implemented within an M2M device (where it is referred to as a deviceSCL (DSCL)), a gateway (where it is referred to as a gateway SCL (GSCL))and/or a network node (where it is referred to as a network SCL (NSCL)).The oneM2M service layer supports a set of Common Service Functions(CSFs) (i.e. service capabilities). An instantiation of a set of one ormore particular types of CSFs is referred to as a Common Services Entity(CSE) which can be hosted on different types of network nodes (e.g.,infrastructure node, middle node, application-specific node). Further,the context-related power control of the present application canimplemented as part of an M2M network that uses a Service OrientedArchitecture (SOA) and/or a resource-oriented architecture (ROA) toaccess services such as the proximity services of the presentapplication.

FIG. 12C is a system diagram of an example M2M device 30, such as an M2Mterminal device 18 or an M2M gateway device 14 shown in FIGS. 12A and12B, or a peer, such as any one of those illustrated in FIGS. 2, 3, and5-9. As shown in FIG. 12C, the M2M device or peer 30 may include aprocessor 32, a transceiver 34, a transmit/receive element 36, aspeaker/microphone 38, a keypad 40, a display/touchpad 42, non-removablememory 44, removable memory 46, a power source 48, a global positioningsystem (GPS) chipset 50, and other peripherals 52. It will beappreciated that the M2M device 30 may include any sub-combination ofthe foregoing elements while remaining consistent with an embodiment.This device may be a device that uses the disclosed systems and methodsfor context-related power control.

The processor 32 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Array (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 32 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the M2M device 30 to operate in a wirelessenvironment. The processor 32 may be coupled to the transceiver 34,which may be coupled to the transmit/receive element 36. While FIG. 12Cdepicts the processor 32 and the transceiver 34 as separate components,it will be appreciated that the processor 32 and the transceiver 34 maybe integrated together in an electronic package or chip. The processor32 may perform application-layer programs (e.g., browsers) and/or radioaccess-layer (RAN) programs and/or communications. The processor 32 mayperform security operations such as authentication, security keyagreement, and/or cryptographic operations, such as at the access-layerand/or application layer for example.

The transmit/receive element 36 may be configured to transmit signalsto, or receive signals from, an M2M service platform 22 or another peer.For example, in an embodiment, the transmit/receive element 36 may be anantenna configured to transmit and/or receive RF signals. Thetransmit/receive element 36 may support various networks and airinterfaces, such as WLAN, WPAN, cellular, and the like. In anembodiment, the transmit/receive element 36 may be an emitter/detectorconfigured to transmit and/or receive IR, UV, or visible light signals,for example. In yet another embodiment, the transmit/receive element 36may be configured to transmit and receive both RF and light signals. Itwill be appreciated that the transmit/receive element 36 may beconfigured to transmit and/or receive any combination of wireless orwired signals.

In addition, although the transmit/receive element 36 is depicted inFIG. 12C as a single element, the M2M device 30 may include any numberof transmit/receive elements 36. More specifically, the M2M device 30may employ MIMO technology. Thus, in an embodiment, the M2M device 30may include two or more transmit/receive elements 36 (e.g., multipleantennas) for transmitting and receiving wireless signals.

The transceiver 34 may be configured to modulate the signals that are tobe transmitted by the transmit/receive element 36 and to demodulate thesignals that are received by the transmit/receive element 36. As notedabove, the M2M device 30 may have multi-mode capabilities. Thus, thetransceiver 34 may include multiple transceivers for enabling the M2Mdevice 30 to communicate via multiple RATs, such as UTRA and IEEE802.11, for example.

The processor 32 may access information from, and store data in, anytype of suitable memory, such as the non-removable memory 44 and/or theremovable memory 46. The non-removable memory 44 may includerandom-access memory (RAM), read-only memory (ROM), a hard disk, or anyother type of memory storage device. The removable memory 46 may includea subscriber identity module (SIM) card, a memory stick, a securedigital (SD) memory card, and the like. In other embodiments, theprocessor 32 may access information from, and store data in, memory thatis not physically located on the M2M device 30, such as on a server or ahome computer. The processor 32 may be configured to control lightingpatterns, images, or colors on the display or indicators 42 in responseto whether the context-related power control (e.g., CPCI information andupdates including states such as whether CPCI detection, inter-P2PNWspower control, or inter-P2PNWs power control occurred) in someembodiments described herein are successful or unsuccessful, orotherwise indicative of the status of context-related power controlpropagation or processing.

The processor 32 may receive power from the power source 48, and may beconfigured to distribute and/or control the power to the othercomponents in the M2M device 30. The power source 48 may be any suitabledevice for powering the M2M device 30. For example, the power source 48may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 32 may also be coupled to the GPS chipset 50, which isconfigured to provide location information (e.g., longitude andlatitude) regarding the current location of the M2M device 30. It willbe appreciated that the M2M device 30 may acquire location informationby way of any suitable location-determination method while remainingconsistent with an embodiment.

The processor 32 may further be coupled to other peripherals 52, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 52 may include anaccelerometer, an e-compass, a satellite transceiver, a sensor, adigital camera (for photographs or video), a universal serial bus (USB)port, a vibration device, a television transceiver, a hands freeheadset, a Bluetooth® module, a frequency modulated (FM) radio unit, adigital music player, a media player, a video game player module, anInternet browser, and the like.

FIG. 12D is a block diagram of an exemplary computing system 90 onwhich, for example, the M2M service platform 22 of FIG. 12A and FIG. 12Bmay be implemented. As mentioned above, certain peers may also beimplemented in the form of computing system 90 or the like. Computingsystem 90 may comprise a computer or server and may be controlledprimarily by computer readable instructions, which may be in the form ofsoftware, wherever, or by whatever means such software is stored oraccessed. Such computer readable instructions may be executed withincentral processing unit (CPU) 91 to cause computing system 90 to dowork. In many known workstations, servers, and personal computers,central processing unit 91 is implemented by a single-chip CPU called amicroprocessor. In other machines, the central processing unit 91 maycomprise multiple processors. Coprocessor 81 is an optional processor,distinct from main CPU 91, that performs additional functions or assistsCPU 91. CPU 91 and/or coprocessor 81 may receive, generate, and processdata related to the disclosed systems and methods for context-relatedpower control, such as receiving CPCI and other context-related powercontrol information over the control plane.

In operation, CPU 91 fetches, decodes, and executes instructions, andtransfers information to and from other resources via the computer'smain data-transfer path, system bus 80. Such a system bus connects thecomponents in computing system 90 and defines the medium for dataexchange. System bus 80 typically includes data lines for sending data,address lines for sending addresses, and control lines for sendinginterrupts and for operating the system bus. An example of such a systembus 80 is the PCI (Peripheral Component Interconnect) bus.

Memory devices coupled to system bus 80 include random access memory(RAM) 82 and read only memory (ROM) 93. Such memories include circuitrythat allows information to be stored and retrieved. ROMs 93 generallycontain stored data that cannot easily be modified. Data stored in RAM82 can be read or changed by CPU 91 or other hardware devices. Access toRAM 82 and/or ROM 93 may be controlled by memory controller 92. Memorycontroller 92 may provide an address translation function thattranslates virtual addresses into physical addresses as instructions areexecuted. Memory controller 92 may also provide a memory protectionfunction that isolates processes within the system and isolates systemprocesses from user processes. Thus, a program running in a first modecan access only memory mapped by its own process virtual address space;it cannot access memory within another process's virtual address spaceunless memory sharing between the processes has been set up.

In addition, computing system 90 may contain peripherals controller 83responsible for communicating instructions from CPU 91 to peripherals,such as printer 94, keyboard 84, mouse 95, and disk drive 85.

Display 86, which is controlled by display controller 96, is used todisplay visual output generated by computing system 90. Such visualoutput may include text, graphics, animated graphics, and video. Display86 may be implemented with a CRT-based video display, an LCD-basedflat-panel display, gas plasma-based flat-panel display, or atouch-panel. Display controller 96 includes electronic componentsrequired to generate a video signal that is sent to display 86.

Further, computing system 90 may contain network adaptor 97 that may beused to connect computing system 90 to an external communicationsnetwork, such as network 12 of FIG. 12A and FIG. 12B.

It is understood that any or all of the systems, methods and processesdescribed herein may be embodied in the form of computer executableinstructions (i.e., program code) stored on a computer-readable storagemedium which instructions, when executed by a machine, such as acomputer, server, M2M terminal device, M2M gateway device, peer, or thelike, perform and/or implement the systems, methods and processesdescribed herein. Specifically, any of the steps, operations orfunctions described above may be implemented in the form of suchcomputer executable instructions. Computer readable storage mediainclude both volatile and nonvolatile, removable and non-removable mediaimplemented in any method or technology for storage of information, butsuch computer readable storage media do not includes signals. Computerreadable storage media include, but are not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other physical medium which can be used to store the desiredinformation and which can be accessed by a computer.

In describing preferred embodiments of the subject matter of the presentdisclosure, as illustrated in the Figures, specific terminology isemployed for the sake of clarity. The claimed subject matter, however,is not intended to be limited to the specific terminology so selected,and it is to be understood that each specific element includes alltechnical equivalents that operate in a similar manner to accomplish asimilar purpose. One skilled in the art will recognize that thedisclosed embodiments may be implemented in architectures and systems,such as 3GPP, ETSI M2M, oneM2M, MQTT, IRTF SDNRG, IRTF P2PRG, IETFCOMAN, IEEE 802.11, IEEE 802.15, IEEE 802.16, IEEE 802 OmniRAN, andother M2M capable systems and architectures.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal languages of the claims.

What is claimed:
 1. A mobile device comprising: a processor; and amemory coupled with the processor, the memory having stored thereonexecutable instructions that when executed by the processor cause theprocessor to effectuate operations comprising: executing multipleservices on the mobile device, the multiple service comprising a firstservice and a second service; while the multiple services are executingon the mobile device at the same time, obtaining default serviceinformation and power control information to control power fortransmitting data, wherein the default service information and powercontrol information comprises first default service information andpower control information for the first service and second defaultservice information and power control information for the secondservice, wherein the first default service information and power controlinformation and the second default service information and power controlinformation are different; detecting scanned service information andpower control information to control power for transmitting data,wherein the scanned service information and power control informationcomprises a first scanned service information and power controlinformation from a first plurality of mobile devices with the firstservice, a second scanned service information and power controlinformation from a second plurality of mobile devices with the secondservice, and a third scanned service and power control information froma third plurality of mobile devices with a third service, wherein thefirst service, second service and third service are different, whereinthe scanned service information and power control information isdetected from at least one common channel; measuring signals receivedfrom other mobile devices in proximity to obtain measured channelinformation and power information, wherein the measured channelinformation and power information comprises a first measured channelinformation and power information to control power from the firstplurality of mobile devices with the first service, a second measuredchannel information and power information to control power from thesecond plurality of mobile devices with the second service, and a thirdmeasured channel and power information to control power from the thirdplurality of mobile devices with the third service, wherein themeasuring of channel information is associated with measured receivedsignal interference and noise ratio, wherein the measuring powerinformation is associated with power or path loss; determining a firstinitial transmit power of the first service and a second initialtransmit power of the second service based on the default serviceinformation and power control information, the scanned serviceinformation and power control information, and the measured channelinformation and power information; and communicating using thedetermined first initial transmit power to a first plurality of peerdevices with the first service in proximity and second initial transmitpower to a second plurality of peer devices with the second service inproximity.
 2. The mobile device of claim 1, wherein a mobile device ofthe first plurality of mobile devices with the first service inproximity is the group lead of the first service network in proximity, amobile device of the second plurality of mobile devices with the secondservice in proximity is the group lead of the second service network inproximity, and a mobile device of the third plurality of mobile deviceswith the third service in proximity is the group lead of the thirdservice network in proximity.
 3. The mobile device of claim 1, whereinthe default service information and power control information is from ahigher layer of the mobile device pre-configured or stored from previouscommunication sessions, and wherein the service information comprisesbandwidth, latency, or speed associated with at least a first service ofthe multiple services, and the power control information comprisesminimum power or maximum power.
 4. The mobile device of claim 1, theoperations further comprising: sending, using the first initial transmitpower and the second initial transmit power, a first power controlrequest for the first service and a second power control request for thesecond service, to the first plurality of mobile devices with the firstservice in which the first plurality of mobile devices are in proximity,a second plurality of mobile devices with the second service in whichthe second plurality of mobile devices are in proximity, and the thirdplurality of mobile devices with the third service in which the thirdplurality of mobile devices are in proximity, wherein the first powercontrol request comprises a request for first service information andpower control information for the first service, wherein the secondpower control request comprises a request for second service informationand power control information for the second service, and wherein thefirst service information and power control information is informationto control power for transmitting data for the first service and thesecond service information and power control information is informationto control power for transmitting data for the second service; based onthe sending, receiving a first plurality of responses to the first powercontrol request and a second plurality of responses to the second powercontrol request from the first plurality of mobile devices with thefirst service in proximity, the second plurality of mobile devices withthe second service in proximity, and the third plurality of mobiledevices with the third service in proximity, wherein the first pluralityof responses or the second plurality of responses comprises the firstservice information and power control information or the second serviceinformation and power control information, wherein the first serviceinformation and power control information or the second serviceinformation and power control information comprises power level or poweradjustment for an associated service; and based on the first serviceinformation and power control information or the second serviceinformation and power control information: determining a first transmitpower for transmitting data for the first service from the mobiledevice, and determining a second transmit power for transmitting datafor the second service from the mobile device.
 5. The mobile device ofclaim 4, the operations further comprising: while the multiple servicesare using multicast and are executing on the mobile device at the sametime, providing instructions to transmit: the data for the first serviceto the first plurality of mobile devices with the first service at thefirst transmit power, and the data for the second service to the secondplurality of mobile devices with the second service at the secondtransmit power, wherein the first transmit power and the second transmitpower are different, wherein the first transmit power is determinedbased on the quality of service of the first service, and the secondtransmit power is determined based on the quality of service of thesecond service.
 6. The mobile device of claim 5, wherein the quality ofservice corresponds to at least guaranteed service and best effortservice.
 7. The mobile device of claim 1, the operations furthercomprising: sending, using the first initial transmit power and thesecond initial transmit power, a first power control request for thefirst service and a second power control request for the second service,to the first plurality of mobile devices with the first service in whichthe first plurality of mobile devices are in proximity, a secondplurality of mobile devices with the second service in which the secondplurality of mobile devices are in proximity, and the third plurality ofmobile devices with the third service in which the third plurality ofmobile devices are in proximity, wherein the first power control requestcomprises a request for first service information and power controlinformation for the first service, wherein the second power controlrequest comprises a request for second service information and powercontrol information for the second service, and wherein the firstservice information and power control information is information tocontrol power for transmitting data for the first service and the secondservice information and power control information is information tocontrol power for transmitting data for the second service; based on thesending, receiving a first plurality of responses to the first powercontrol request and a second plurality of responses to the second powercontrol request from the first plurality of mobile devices with thefirst service in proximity, the second plurality of mobile devices withthe second service in proximity, and the third plurality of mobiledevices with the third service in proximity, wherein the first pluralityof responses or the second plurality of responses comprises the firstservice information and power control information or the second serviceinformation and power control information, wherein the first serviceinformation and power control information or the second serviceinformation and power control information comprises power level or poweradjustment for an associated service; and based on the first serviceinformation and power control information or the second serviceinformation and power control information of the response: determining afirst transmit power for transmitting data for the first service fromthe mobile device, and determining a second transmit power fortransmitting data for the second service from the mobile device;providing instructions to transmit: data for the first service to thefirst mobile device with the first service at the first transmit power,and data for the second service to the second mobile device with thesecond service at the second transmit power, wherein the first transmitpower and the second transmit power are different, wherein the multipleservices use unicast while executing on the mobile device at the sametime, wherein the unicast is one-to-one communication between two mobiledevices with the same service.
 8. A method for managing power in awireless network, the method comprising: executing multiple services ona mobile device, the multiple service comprising a first service and asecond service; while the multiple services are executing on the mobiledevice at the same time, obtaining default service information and powercontrol information to control power for transmitting data, wherein thedefault service information and power control information comprisesfirst default service information and power control information for thefirst service and second default service information and power controlinformation for the second service, wherein the first default serviceinformation and power control information and the second default serviceinformation and power control information are different; detectingscanned service information and power control information to controlpower for transmitting data, wherein the scanned service information andpower control information comprises a first scanned service informationand power control information from a first plurality of mobile deviceswith the first service, a second scanned service information and powercontrol information from a second plurality of mobile devices with thesecond service, and a third scanned service and power controlinformation from a third plurality of mobile devices with a thirdservice, wherein the first service, second service and third service aredifferent, wherein the scanned service information and power controlinformation is detected from at least one channel; measuring signalsreceived from other mobile devices in proximity to obtain measuredchannel information and power information, wherein the measured channelinformation and power information comprises a first measured channelinformation and power information to control power from the firstplurality of mobile devices with the first service, a second measuredchannel information and power information to control power from thesecond plurality of mobile devices with the second service, and a thirdmeasured channel and power information to control power from the thirdplurality of mobile devices with the third service, wherein themeasuring of channel information is associated with measured receivedsignal interference and noise ratio, wherein the measuring powerinformation is associated with power and path loss; determining a firstinitial transmit power of the first service and a second initialtransmit power of the second service based on the default serviceinformation and power control information, the scanned serviceinformation and power control information, and the measured channelinformation and power information; and communicating using thedetermined first initial transmit power to a first plurality of peerdevices with the first service in proximity and second initial transmitpower to a second plurality of peer devices with the second service inproximity.
 9. The method of claim 8, wherein a mobile device of thefirst plurality of mobile devices with the first service in proximity isthe group lead of the first service network in proximity, a mobiledevice of the second plurality of mobile devices with the second servicein proximity is the group lead of the second service network inproximity, and a mobile device of the third plurality of mobile deviceswith the third service in proximity is the group lead of the thirdservice network in proximity.
 10. The method of claim 8, wherein thedefault service information and power control information is from ahigher layer of the mobile device pre-configured or stored from previouscommunication sessions, and wherein the service information comprisesbandwidth, latency, and speed associated with at least a first serviceof the multiple services, and the power control information comprisesminimum power or maximum power.
 11. The method of claim 8, furthercomprising: sending, using the first initial transmit power and thesecond initial transmit power, a first power control request for thefirst service and a second power control request for the second service,to the first plurality of mobile devices with the first service in whichthe first plurality of mobile devices are in proximity, a secondplurality of mobile devices with the second service in which the secondplurality of mobile devices are in proximity, and the third plurality ofmobile devices with the third service in which the third plurality ofmobile devices are in proximity, wherein the first power control requestcomprises a request for first service information and power controlinformation for the first service, wherein the second power controlrequest comprises a request for second service information and powercontrol information for the second service, and wherein the firstservice information and power control information is information tocontrol power for transmitting data for the first service and the secondservice information and power control information is information tocontrol power for transmitting data for the second service; based on thesending, receiving a first plurality of responses to the first powercontrol request and a second plurality of responses to the second powercontrol request from the first plurality of mobile devices with thefirst service in proximity, the second plurality of mobile devices withthe second service in proximity, and the third plurality of mobiledevices with the third service in proximity, wherein the first pluralityof responses or the second plurality of responses comprises the firstservice information and power control information or the second serviceinformation and power control information, wherein the first serviceinformation and power control information or the second serviceinformation and power control information comprises power level andpower adjustment for an associated service; and based on the firstservice information and power control information or the second serviceinformation and power control information: determining a first transmitpower for transmitting data for the first service from the mobiledevice, and determining a second transmit power for transmitting datafor the second service from the mobile device.
 12. The method of claim11, further comprising: while the multiple services are using multicastand are executing on the mobile device at the same time, providinginstructions to transmit: the data for the first service to the firstplurality of mobile devices with the first service at the first transmitpower, and the data for the second service to the second plurality ofmobile devices with the second service at the second transmit power,wherein the first transmit power and the second transmit power aredifferent, wherein the first transmit power is determined based on thequality of service of the first service, and the second transmit poweris determined based on the quality of service of the second service. 13.The method of claim 12, wherein the quality of service corresponds to atleast guaranteed service and best effort service.
 14. The method ofclaim 8, further comprising: sending, using the first initial transmitpower and the second initial transmit power, a first power controlrequest for the first service and a second power control request for thesecond service, to the first plurality of mobile devices with the firstservice in which the first plurality of mobile devices are in proximity,a second plurality of mobile devices with the second service in whichthe second plurality of mobile devices are in proximity, and the thirdplurality of mobile devices with the third service in which the thirdplurality of mobile devices are in proximity, wherein the first powercontrol request comprises a request for first service information andpower control information for the first service, wherein the secondpower control request comprises a request for second service informationand power control information for the second service, and wherein thefirst service information and power control information is informationto control power for transmitting data for the first service and thesecond service information and power control information is informationto control power for transmitting data for the second service; based onthe sending, receiving a first plurality of responses to the first powercontrol request and a second plurality of responses to the second powercontrol request from the first plurality of mobile devices with thefirst service in proximity, the second plurality of mobile devices withthe second service in proximity, and the third plurality of mobiledevices with the third service in proximity, wherein the first pluralityof responses or the second plurality of responses comprises the firstservice information and power control information or the second serviceinformation and power control information, wherein the first serviceinformation and power control information or the second serviceinformation and power control information comprises power level or poweradjustment for an associated service; and based on the first serviceinformation and power control information or the second serviceinformation and power control information: determining a first transmitpower for transmitting data for the first service from the mobiledevice, and determining a second transmit power for transmitting datafor the second service from the mobile device; providing instructions totransmit: data for the first service to the first mobile device with thefirst service at the first transmit power, and data for the secondservice to the second mobile device with the second service at thesecond transmit power, wherein the first transmit power and the secondtransmit power are different, wherein the multiple services use unicastwhile executing on the mobile device at the same time, wherein theunicast is one-to-one communication between two mobile devices with thesame service.
 15. A non-transitory computer readable storage mediumstoring computer executable instructions that when executed by acomputing device cause said computing device to effectuate operationscomprising: executing multiple services on a mobile device, the multipleservice comprising a first service and a second service; while themultiple services are executing on the mobile device at the same time,obtaining default service information and power control information tocontrol power for transmitting data, wherein the default serviceinformation and power control information comprises first defaultservice information and power control information for the first serviceand second default service information and power control information forthe second service, wherein the first default service information andpower control information and the second default service information andpower control information are different; detecting scanned serviceinformation and power control information to control power fortransmitting data, wherein the scanned service information and powercontrol information comprises a first scanned service information andpower control information from a first plurality of mobile devices withthe first service, a second scanned service information and powercontrol information from a second plurality of mobile devices with thesecond service, and a third scanned service and power controlinformation from a third plurality of mobile devices with a thirdservice, wherein the first service, second service and third service aredifferent, wherein the scanned service information and power controlinformation is detected from at least one channel; measuring signalsreceived from other mobile devices in proximity to obtain measuredchannel information and power information, wherein the measured channelinformation and power information comprises a first measured channelinformation and power information to control power from the firstplurality of mobile devices with the first service, a second measuredchannel information and power information to control power from thesecond plurality of mobile devices with the second service, and a thirdmeasured channel and power information to control power from the thirdplurality of mobile devices with the third service, wherein themeasuring of channel information is associated with measured receivedsignal interference and noise ratio, wherein the measuring powerinformation is associated with power and path loss; determining a firstinitial transmit power of the first service and a second initialtransmit power of the second service based on the default serviceinformation and power control information, the scanned serviceinformation and power control information, and the measured channelinformation and power information; and communicating using thedetermined first initial transmit power to a first plurality of peerdevices with the first service in proximity and second initial transmitpower to a second plurality of peer devices with the second service inproximity.
 16. The non-transitory computer readable storage medium ofclaim 15, wherein a mobile device of the first plurality of mobiledevices with the first service in proximity is the group lead of thefirst service network in proximity, a mobile device of the secondplurality of mobile devices with the second service in proximity is thegroup lead of the second service network in proximity, and a mobiledevice of the third plurality of mobile devices with the third servicein proximity is the group lead of the third service network inproximity.
 17. The non-transitory computer readable storage medium ofclaim 15, wherein the default service information and power controlinformation is from a higher layer of the mobile device pre-configuredor stored from previous communication sessions, and wherein the serviceinformation comprises bandwidth, latency, or speed associated with atleast a first service of the multiple services, and the power controlinformation comprises minimum power and maximum power.
 18. Thenon-transitory computer readable storage medium of claim 15, theoperations further comprising: sending, using the first initial transmitpower and the second initial transmit power, a first power controlrequest for the first service and a second power control request for thesecond service, to the first plurality of mobile devices with the firstservice in which the first plurality of mobile devices are in proximity,a second plurality of mobile devices with the second service in whichthe second plurality of mobile devices are in proximity, and the thirdplurality of mobile devices with the third service in which the thirdplurality of mobile devices are in proximity, wherein the first powercontrol request comprises a request for first service information andpower control information for the first service, wherein the secondpower control request comprises a request for second service informationand power control information for the second service, and wherein thefirst service information and power control information is informationto control power for transmitting data for the first service and thesecond service information and power control information is informationto control power for transmitting data for the second service; based onthe sending, receiving a first plurality of responses to the first powercontrol request and a second plurality of responses to the second powercontrol request from the first plurality of mobile devices with thefirst service in proximity, the second plurality of mobile devices withthe second service in proximity, and the third plurality of mobiledevices with the third service in proximity, wherein the first pluralityof responses or the second plurality of responses comprises the firstservice information and power control information or the second serviceinformation and power control information, wherein the first serviceinformation and power control information or the second serviceinformation and power control information comprises power level andpower adjustment for an associated service; and based on the firstservice information and power control information or the second serviceinformation and power control information: determining a first transmitpower for transmitting data for the first service from the mobiledevice, and determining a second transmit power for transmitting datafor the second service from the mobile device.
 19. The non-transitorycomputer readable storage medium of claim 18, the operations furthercomprising: while the multiple services are using multicast and areexecuting on the mobile device at the same time, providing instructionsto transmit: the data for the first service to the first plurality ofmobile devices with the first service at the first transmit power, andthe data for the second service to the second plurality of mobiledevices with the second service at the second transmit power, whereinthe first transmit power and the second transmit power are different,wherein the first transmit power is determined based on the quality ofservice of the first service, and the second transmit power isdetermined based on the quality of service of the second service. 20.The non-transitory computer readable storage medium of claim 15, theoperations further comprising: sending, using the first initial transmitpower and the second initial transmit power, a first power controlrequest for the first service and a second power control request for thesecond service, to the first plurality of mobile devices with the firstservice in which the first plurality of mobile devices are in proximity,a second plurality of mobile devices with the second service in whichthe second plurality of mobile devices are in proximity, and the thirdplurality of mobile devices with the third service in which the thirdplurality of mobile devices are in proximity, wherein the first powercontrol request comprises a request for first service information andpower control information for the first service, wherein the secondpower control request comprises a request for second service informationand power control information for the second service, and wherein thefirst service information and power control information is informationto control power for transmitting data for the first service and thesecond service information and power control information is informationto control power for transmitting data for the second service; based onthe sending, receiving a first plurality of responses to the first powercontrol request and a second plurality of responses to the second powercontrol request from the first plurality of mobile devices with thefirst service in proximity, the second plurality of mobile devices withthe second service in proximity, and the third plurality of mobiledevices with the third service in proximity, wherein the first pluralityof responses or the second plurality of responses comprises the firstservice information and power control information or the second serviceinformation and power control information, wherein the first serviceinformation and power control information or the second serviceinformation and power control information comprises power level andpower adjustment for an associated service; and based on the firstservice information and power control information or the second serviceinformation and power control information: determining a first transmitpower for transmitting data for the first service from the mobiledevice, and determining a second transmit power for transmitting datafor the second service from the mobile device; providing instructions totransmit: data for the first service to the first mobile device with thefirst service at the first transmit power, and data for the secondservice to the second mobile device with the second service at thesecond transmit power, wherein the first transmit power and the secondtransmit power are different, wherein the multiple services use unicastwhile executing on the mobile device at the same time, wherein theunicast is one-to-one communication between two mobile devices with thesame service.